Create a new wiki page entitled WA2 and insert the following::
1. Heading: Web Activity Two
2. A link to your revised, final version of WA1. This can be your same WA1 site that you have revised. You can use the same URL, OK ?!
3. A thorough explanation of the changes you have made and the reasons for making those changes.
4. Due by midnight on Wednesday, October 7.
Here are some examples of WA2:
(Example One) Web Activity Two:
Please check out my edited page above. Below is a list of changes I made. Thank you for your feedback! :)
I made the logo larger because it was too small to see. I was afraid of going over the 100K limit, but it seems to be under 100K still even though I made it larger.
On the "Day 1" page, I made the images under 100K without making them too tiny.
I changed all of the links on the sidebar to make sure they were working properly for each page.
I added "Day 2" and "Day 3" pages because I didn't want those to be empty links on the sidebar.
I completely changed my folder setup on my computer because it was getting confusing to me (I did this before editing the links in Dreamweaver).
I sent the entire folder to Fetch.
I double checked the links, picture sizes, Youtube video, headings, and email link.
(Example Two) Web Activity Two
Drum roll, please...Here's my new and improved site. .....[NA] Thank you all for the very helpful feedback. This is what I changed:
The "stone face" image originally did not have an attribution, so I added that.
Through a three-hour process of lots of trial and even more error, I was able to "fix" the third page of YouTube videos that lost the original formatting. In order to do this, I had to completely rebuild the third page. I went to Kompozer, opened my index page, "saved as" carterpage2 and then re-embedded the YouTube media, repaired the links, and saved. Before sending it to my domain through the FTP, I changed the page title settings from xhtml to just html. I don't really know why that works, but it did...
I tried to go into the html code to make the size of the YouTube players the same, but was never able to do that correctly.
Two "home" links were redundant, so I deleted the one in the upper right-hand corner.
The heading for the navigation bar on the left orginally said "Read and View the Speech," which was redundant. I changed that to a more accurate and precise header - "Assignment Resources."
I fixed the erroneous link on page 2 ("Read the Speech").
I fixed the window titles - each page has a specific title all its own.
Originally, the navigation bar "moved" when you moved from page to page because of differing font sizes and the skull picture being in slightly different locations on each page. When I rebuilt my third page, this gave me the opportunity to fix that as well. Since I "saved as" from the index page, the navigation bar doesn't appear to shift when a user clicks between the pages.
I considered making the font larger, but because it broke the lines of the speech (I'm using a pre-made CSS template), I decided to keep it the same - I figured my students' eyes are a bit younger than ours. (It is 12-point, so I didn't feel like it really needed to be changed.)
I polished my write-up a bit. (For example, instead of saying the "style guide," I changed that to the "Web Style Guide.")
I also tried to make this page a bit more user friendly (added in anchors and internal links and used font colors that helped the eyes).
(Example Three) Web Activity Two
Changes made to web activity one:
1. The main change I made was the layout and design of the site. I did this because feedback said it was difficult to use the drop down menu on the original webpage. Also, I really wanted have a more professional looking website, so I used a template! 2. I also added more content to describe how Algebra Tiles are used. Feed back was given from a non-mathematical point of view stating that it would be difficult for them to use the site because they have a very limited background in math. I tried to give better explanations of each step and descriptions to how algebra tiles were suppose to be used. I also used this feedback to change the way pictures were displayed on the website. I feel that having small thumbnails that enlarge for each step will make the content more easy to understand with each text description.3. The resource page needed a major make over, so I changed the layout to make the featured items more accessible and easier to understand. I received feed back about my resource page having typos and needing clarification about items listed.4. I also changed the folder name to the correct folder name, however, I did not change the the individual page names. My reason for not changing each individual page name to smoot1.html, smoot2.html, etc...is because of how many pages I have on my site. Naming the pages more appropriately about the content seemed more realistic and easier to manage when creating links between pages.
(Example Four) Web Activity Two
The comments from WA1 were helpful in evaluating my site for potential changes in WA2. In general, my first site met the basic requirements, and I wanted to streamline a couple of sections to further the content flow and accessibility of information.
Tami, thank you for noting your issue with IE overlaying the video content over the thickbox component. This actually brings up an excellent point regarding proper web site testing. When the audience of computers is undefined (for a public site, as opposed to a controlled intranet site), you must test the final site with a variety of web browsers to ensure that the content is displayed correctly. I normally test with a standard test suite of Safari, Firefox, Internet Explorer 7, and Internet Explorer 6 (IE6 has numerous display issues, and the lack of native support for png images). I researched the issue more thoroughly, and it appears that the ActiveX structure that contains the flash movie renders above all layers of CSS content. At this point, I am still researching methods to hide the video content while the thickbox is overlayed. I have tried a standard CSS property change, setting display to none, but this does not hide plug-in content in this instance. I will continue looking for a solution for this issue.
Another potential issue was the accessibility functionality of the thickbox component. The component creates a new div tag with visible content on click, so the general issue of readability is mitigated. If the user does not have javascript enabled (as many accessibility users do not), the link functions as a standard link, and the user is sent to a separate page for the content, instead of the content loading inline with AJAX. This is considered a fairly standard fallback protocol, and meets all necessary accessibility guidelines. I would like to attempt to make some of the popup content more accessible from a "bookmarkable" perspective, by making each section available as page anchors (#mondrian, for example). This tactic is generally acknowledged as a helpful gesture for pages with content loaded through AJAX or other inline technologies. Once again, some functionality has been developed within the jquery project to allow AJAX-based browser history, but this featureset has not been extended to thickbox as of yet. I will look into modifying this functionality further. (Example Five) Web Activity Two
Below is a list of changes made to the original site:
On the index page I fixed to problems with the slider. One problem included a typo in the destination name for an image and the other involved centering the slider photo on the actual weimaraner. I used Preview on the Mac to make this adjustment.
Per feedback, I also added credits (with links to 3rd party originals) to all images on index.html. Two of the color photos came from Wikimedia Commons, and I credited the actual author when listed. For the slider photos and "loyal companion" color photo, I added my own name.
Also from feedback, I removed both advertising in the footer and the search box. on each page.
Again, thanks to feedback, I fixed the "homepage" top link to point to this project's index page and not my general domain.
On runner.html I added a slider with resized images from Wikimedia Commons. All images depict the weimaraner in running positions or activities. I added a lined caption on the slider to the original photos. I also removed the "The Weimaraner" linked header to the homepage because I could not for the life of me get it to look right with the slider. I will undoubtedly continue to work on this so by the time you read this you may very well see it!
I added a new page, hunter.html. This page includes a description of the breed's hunting capabilities, as well as a quote and link to an article in GunDog Magazine. In an effort to provide consistency, as described by Web Style Guide, I built the page off of the design for runner.html. I embedded a YouTube video of weimaraners hunting, and I added slider photos depicting the breed in hunting or pointing images. All slider images are captioned with a link to the original photos on Wikimedia Commons.
Lastly, I double-checked image sizes (all less than 100K) and links.
Create a new wiki page entitled WA2 and insert the following::
Here are some examples of WA2:
(Example One) Web Activity Two:
Please check out my edited page above. Below is a list of changes I made. Thank you for your feedback! :)
(Example Two) Web Activity Two
Drum roll, please...Here's my new and improved site. .....[NA]Thank you all for the very helpful feedback. This is what I changed:
(Example Three) Web Activity Two
Changes made to web activity one:
1. The main change I made was the layout and design of the site. I did this because feedback said it was difficult to use the drop down menu on the original webpage. Also, I really wanted have a more professional looking website, so I used a template!
2. I also added more content to describe how Algebra Tiles are used. Feed back was given from a non-mathematical point of view stating that it would be difficult for them to use the site because they have a very limited background in math. I tried to give better explanations of each step and descriptions to how algebra tiles were suppose to be used. I also used this feedback to change the way pictures were displayed on the website. I feel that having small thumbnails that enlarge for each step will make the content more easy to understand with each text description.3. The resource page needed a major make over, so I changed the layout to make the featured items more accessible and easier to understand. I received feed back about my resource page having typos and needing clarification about items listed.4. I also changed the folder name to the correct folder name, however, I did not change the the individual page names. My reason for not changing each individual page name to smoot1.html, smoot2.html, etc...is because of how many pages I have on my site. Naming the pages more appropriately about the content seemed more realistic and easier to manage when creating links between pages.
(Example Four) Web Activity Two
The comments from WA1 were helpful in evaluating my site for potential changes in WA2. In general, my first site met the basic requirements, and I wanted to streamline a couple of sections to further the content flow and accessibility of information.
Tami, thank you for noting your issue with IE overlaying the video content over the thickbox component. This actually brings up an excellent point regarding proper web site testing. When the audience of computers is undefined (for a public site, as opposed to a controlled intranet site), you must test the final site with a variety of web browsers to ensure that the content is displayed correctly. I normally test with a standard test suite of Safari, Firefox, Internet Explorer 7, and Internet Explorer 6 (IE6 has numerous display issues, and the lack of native support for png images). I researched the issue more thoroughly, and it appears that the ActiveX structure that contains the flash movie renders above all layers of CSS content. At this point, I am still researching methods to hide the video content while the thickbox is overlayed. I have tried a standard CSS property change, setting display to none, but this does not hide plug-in content in this instance. I will continue looking for a solution for this issue.
Another potential issue was the accessibility functionality of the thickbox component. The component creates a new div tag with visible content on click, so the general issue of readability is mitigated. If the user does not have javascript enabled (as many accessibility users do not), the link functions as a standard link, and the user is sent to a separate page for the content, instead of the content loading inline with AJAX. This is considered a fairly standard fallback protocol, and meets all necessary accessibility guidelines. I would like to attempt to make some of the popup content more accessible from a "bookmarkable" perspective, by making each section available as page anchors (#mondrian, for example). This tactic is generally acknowledged as a helpful gesture for pages with content loaded through AJAX or other inline technologies. Once again, some functionality has been developed within the jquery project to allow AJAX-based browser history, but this featureset has not been extended to thickbox as of yet. I will look into modifying this functionality further.
(Example Five) Web Activity Two
Below is a list of changes made to the original site: